home *** CD-ROM | disk | FTP | other *** search
- Path: engnews1.Eng.Sun.COM!taumet!clamage
- From: "Nathan Myers, http://www.cantrip.org/" <ncm@cantrip.org>
- Newsgroups: comp.std.c++
- Subject: Re: Time representations
- Date: 2 Feb 1996 15:49:18 GMT
- Organization: The Cantrip Cooperative
- Approved: clamage@eng.sun.com (comp.std.c++)
- Message-ID: <31121F55.139E@cantrip.org>
- References: <4emq2k$ecu@news.duke.edu>
- NNTP-Posting-Host: taumet.eng.sun.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset="us-ascii"
- Content-Transfer-Encoding: 7bit
- X-Nntp-Posting-Host: ncm.vip.best.com
- X-Mailer: Mozilla 2.0b6a (X11; I; SunOS 5.4 sun4m)
- X-Lines: 24
- Content-Length: 998
- Originator: clamage@taumet
-
- Max TenEyck Woodbury wrote:
- >
- > The C++ standard incorporates the C standard for dates and times
- > by reference. There are at least three problems with the 'struct tm'
- > definition in that standard.
- > ...
- > Second, there are cultures that operate on a lunar calendar,
- > rather than on the Gregorian calendar. They have 13 or more months
- > a year. The tm_mon range needs to reflect this.
- >
- > Third, there are cultures that do not start their year on January
- > 1st. This has an impact on the definition of tm_yday even though
- > its range will not change. There is a similar definitional problem
- > with tm_year. ...
-
- The C++ Library (Draft!) standard is not as restrictive
- as Woodbury suggests. It is capable of representing
- Gregorian dates, but does not in any way enforce them.
- It does expect that any other date is convertible into
- a Gregorian date (and a Julian), but that's a much weaker
- restriction.
-
- Nathan Myers
- ncm@cantrip.org http://www.cantrip.org/ <-- works now.
-
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy is
- summarized in http://reality.sgi.com/employees/austern_mti/std-c++/policy.html
- ]
-